Skip to content

Introduce BindingProxy to mitigate temporary XAML binding failures#4045

Merged
Keboo merged 2 commits intomasterfrom
fix3814
May 1, 2026
Merged

Introduce BindingProxy to mitigate temporary XAML binding failures#4045
Keboo merged 2 commits intomasterfrom
fix3814

Conversation

@nicolaihenriksen
Copy link
Copy Markdown
Contributor

Fixes #3814

Introduces a BindingProxy to mitigate the temporary binding failures occurring when bindings are used to reference something not in the current visual tree.

The issue was easily reproducible. I also went through the pages of the demo app (just opening them) to spot any immediate XAML binding failures. There were 2 apart from the ProgressBar:

  • Slider (fixed, also using BindingProxy)
  • Tree (not fixed, this seems to be a different issue)
image

@nicolaihenriksen nicolaihenriksen added this to the 5.3.2 milestone Apr 24, 2026
@Keboo Keboo enabled auto-merge (squash) May 1, 2026 04:57
Moves `BindingProxy` to the `MaterialDesignThemes.Wpf.Internal` namespace and marks it as `sealed`. This change clarifies that `BindingProxy` is an internal implementation detail of the library, preventing direct external usage or inheritance and helping to maintain a cleaner public API surface.

Relates to #3814
@Keboo Keboo merged commit 836e12b into master May 1, 2026
2 checks passed
@Keboo Keboo deleted the fix3814 branch May 1, 2026 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

XAML Binding Failures when ProgressBar is styled with MaterialDesignCircularProgressBar in v5.2.1 (Was working in v5.1.0)

2 participants